212 replies to this topic

[AsosaYoung]

More .84 have risen from the dead like Lazarus... TY Geezus now welcome to the Walking Dead

Sent from my DROID RAZR using Tapatalk 2

[kaplac]

huzzah!

10/10 unique confirmations!

If you've been waiting for this to be confirmed then here it is!

This fix has been confirmed for restoring .84 or .85 from a softbricked phone.
It will only restore your phone back to it's last working rom (that means you can't go from .84 to .85)

All thanks go to KBoss805 and the testers who have confirmed this fix to be working.

[nailbomb3]

Progress! Kickass!

[Gerland the Oracle]

Am going too attempt when i get off work in about 3hrs, Here's hoping!!!

[jpcalhoun]

This thread ought to be on the front page...just like the one that got us in this spot was. Not bitc$%#g, I love .84, but it is time consuming to find this "fix" and it looks like a life saver for a lot of bricked razr owners.

[xlightwaverx]

This fix has been confirmed for restoring .84 or .85 from a softbricked phone.
It will only restore your phone back to it's last working rom (that means you can't go from .84 to .85)

Why can't you just use the .85 update after you .181 the system, so then all bricked users will actually be at the latest ICS release?

X

[jpcalhoun]

Why can't you just use the .85 update after you .181 the system, so then all bricked users will actually be at the latest ICS release?

X

I don't understand all the tech reasons but it has been tried and it does not work.

[EmericanX]

I'm gonna attempt it again tonight. But I can tell you after 5 failed attempts at flashing .85 I put the update for .84 on my sdcard... then flashed. It won't through completely on the first attempt.. and booted. Why? I'm not 100% sure yet because it shouldn't matter.

Sent from my Galaxy Nexus using Tapatalk 2

[(TSON)]

make sure you let us know where it errors out

[EmericanX]

I was failing on assert-fail boot: then a bunch of other info.. lol. To me it looked as if it was comparing md5 of the boot.img

Sent from my Galaxy Nexus using Tapatalk 2

[MkVsTheWorld]

Why can't you just use the .85 update after you .181 the system, so then all bricked users will actually be at the latest ICS release?

X

I don't understand all the tech reasons but it has been tried and it does not work.

It's due to that pesky bootloader not letting you go back. So, you can fix your phone with this method if you are soft-bricked with either of the 84/85 leaks but there isn't a way to manipulate the bootloader to flash back to the GB releases. Once the official ICS OTA comes out, I don't think there will be as many people wanting to flash back to GB.

[jpcalhoun]

It's due to that pesky bootloader not letting you go back. So, you can fix your phone with this method if you are soft-bricked with either of the 84/85 leaks but there isn't a way to manipulate the bootloader to flash back to the GB releases. Once the official ICS OTA comes out, I don't think there will be as many people wanting to flash back to GB.

Yeah, not sure why anyone want to go back to GB, unless there is a ROM that they can't live without.

[wyld]

Yeah, not sure why anyone want to go back to GB, unless there is a ROM that they can't live without.

To get back on the proper upgrade path.

Sent from my DROID RAZR using Tapatalk 2

[tucstwo]

Yeah, not sure why anyone want to go back to GB, unless there is a ROM that they can't live without.

People want to have the ability to fastboot back for 2 main reasons.

• So they can satisfy their crackflashing and continue for flash roms and things the like.
• So that they are already prepared for when the "Official" ICS OTA is pushed by big red instead of scrambling around afterwards.

[xlightwaverx]

I was failing on assert-fail boot: then a bunch of other info.. lol. To me it looked as if it was comparing md5 of the boot.img

Sent from my Galaxy Nexus using Tapatalk 2

I'm gonna attempt it again tonight. But I can tell you after 5 failed attempts at flashing .85 I put the update for .84 on my sdcard... then flashed. It won't through completely on the first attempt.. and booted. Why? I'm not 100% sure yet because it shouldn't matter.

Sent from my Galaxy Nexus using Tapatalk 2

I don't understand all the tech reasons but it has been tried and it does not work.

So .84 can brute force .181 back, then .84 back up...
.85 can brute force .181 back, and then only .84 up...

So there is a difference between the .84 and .85 bootloaders?

Sorry for the little pesky things, but stuff like this means a lot to me when figuring out how these mototards work. As if it was on purpose this whole fiasco happened, because two versions, released so close apart, fairly the same, with different bootloaders seems to be an attack of the crackflasher.

Just my opinion...

X

[kboss805]

This thread ought to be on the front page...just like the one that got us in this spot was. Not bitc$%#g, I love .84, but it is time consuming to find this "fix" and it looks like a life saver for a lot of bricked razr owners.

How do you go about getting it on the front Page?

Sent from my DROID RAZR using Tapatalk 2

[kboss805]

+1. Mods can this please be put on the main page since this is a confirmed fix? By the way kboss805, good stuff man. You saved a lot of peoples phones.

Necessity is the mother of all invention

Sent from my DROID RAZR using Tapatalk 2

[Thach]

Done, I moved it to the front page news since this is working so well and we need to get the word out to everyone with soft bricks.

[xlightwaverx]

Can someone post a list of the failed imgs that did not get fastbooted back when someone tries to .181 a .85 or .84 system?

Thanks

X